Bytecode verifier is failing with try-catch statements

[ShadelessFox]

A bytecode verification feature was added in aa6aab1, but the code we're emitting for try-catch statements (#22, a9e3cbe) is not valid. Consider following code snippet:

try {
    return 1;
} finally {
    return 2;
}

It will generate following bytecode:

00000000 01 00 00 PUSH         2
00000003 19       RETURN       
00000004 01 00 01 PUSH         1
00000007 19       RETURN       
00000008 01 00 00 PUSH         2
0000000b 19       RETURN       
0000000c 01 00 00 PUSH         2
0000000f 19       RETURN       
00000010 07 00    GET_LOCAL    0
00000012 01 00 02 PUSH         none
00000015 1d       CMP_EQ       
00000016 1b 00 03 JUMP_IF_TRUE 3 (#L01)
00000019 07 00    GET_LOCAL    0
0000001b 2a       THROW        

Notice how weird it is and how many times the body of finally is repeated. The verifier itself is complaining about jump at 16 that is pointing literally nowhere (beyond the chunk itself), this should not happen.