Make jump target comparison inclusive (<=) rather than strict (<).
Make jump target comparison inclusive (<=) rather than strict (<).

This is important because jumping to the very end of the try block is
typically the same as jumping to the very beginning of the finally block
if there is no catch handler. As the comment indicates, the finally block
should only be triggered if the jump target falls *outside* the region
governed by the finally block.

Fixes #192.

kittens/regenerator,juliocanares/regenerator,facebook/regenerator,rafaelstz/regenerator,kittens/regenerator,liviuignat/regenerator,RReverser/js-goto-transpiler,sebmck/regenerator,RReverser/js-goto-transpiler,facebook/regenerator,juliocanares/regenerator,sebmck/regenerator,liviuignat/regenerator,rafaelstz/regenerator,facebook/regenerator