gameba - thanks for the bug report. Had me concerned for a while, but thankfully it was caused by floating point errors in the polygon decomposition function - that polygon shape in frame 2 was perfect to reproduce it, for some reason.
Update: v1.05
Bug fixes:
Floating point error compensation in the complex polygon decomp function
Fix possibility of incorrect object refs causing errors when they are destroyed