AOP can do a lot of things but it can't clean up poorly structured code.
I'm a lurker on the AspectJ-Users and AspectJ-Dev mailing lists. Good nuggets often pop up there that should be disseminated to a larger audience.
Sven Apel was asking the list for a way to advise a for-loop construct. Ron Bodkin pointed out that "to use AspectJ with code like this, you could use the extract method refactoring, which would let you name a helper method to describe the post inner-loop behavior you want to advise."