OO bug test failure mysticism

Hi there, although operating in stealth mode I am still there ;) For all those who are curious about this OO bug test... I am responsible; no it is ZE1 and will be fixed by ZE2 (never tested, but ought to). It was just placed there to ensure to not to forget about *copies* (of the objects created) given back by the "new" statement (or the constructor if you like) by default, what introduced the need for this work-around-hack-thing-tutorial I introduced to the documentation. In brief, let it fail :) nobody cares. Would be interesting if ZE2 already fixes it, though. Has anyone played with it and is the patch/hack construct prone to BC-issues? If so, it should be mentioned in the release notes as a migration note. Regards, André ps. Do not expect replies to this being answered before the end of next week, I will be knocked out for about one week from now on.