I've noticed that IE10, unlike IE9, no longer supports arguments.callee.caller (strict mode is on, and I don't know how to turn it off). In the 'propaganda' ( ;) ) I read that this is because the whole arguments.callee.caller is considered unsafe. And since a recursive function would mess it up (infinite .caller references to the same instance-call), I'll admit you have a point.
I noticed this because I was and am working on a better tracelog (one that spans recursive functions, callbacks, eventhandlers, setTimeout and setInterval) for all browser apps, I call it "hipLog". You can see a demo of it (use chrome for now) at http://fancywebapps.com, then after loading press the light-blue-white-colored button in the bottom right of your browser window.
The data for that view you'll see then is collected by http://fancywebapps.com/fancywebapps/com/core/fwaTrace-1.0.0.source.js (230 lines), and it uses arguments.callee.caller in a SAFE and USEFUL way.
I'm gonna have to ask for a way to put IE10 in IE9 mode, and also ask that in future versions of IE you keep the arguments.callee.caller functionality available, and possibly improve it by fixing that recursive-function usecase for it.
With regards, and thanks for keeping IE a free app,
Rene