Thanks for reporting this! I believe it might be related to an optimization I added... I'll see if I can reverse it or fix that bug before pushing a new version out.