Make visitTryCatchBlock respect nesting
I couldn't find mention of this in the documentation, but experimentation has shown that exception handlers are tested based on the order of their registration with visitTryCatchBlock (just like the underlying class definition works — try-catch blocks are scanned in order). This is inconvenient, especially because ASM's visitor architecture so nicely supports nesting of things. This makes it hard to break up a code generation into several methods. I think it would be great if visitTryCatchBlock would respect nesting — just as it works in Java (and any other JVM language).