This uncovered a few hidden errors in the management of frames and
frame contexts:
- Pop_Frame_Context was missing when capturing a closure
- Top_Object was not updated when pushing or popping a frame
- Top_Oject was not properly retreived in function calls
One of these cleanup turned out to be the behavior of allocators in the
context of calls that are generating all values, e.g. in:
child (new (something ())).all ()
Turns out there's no reason to forbid this, the natural semantic is that a
new object will be created for all child of the current it.
