I believe this information was represented differently within the runtime server, resulting in the debugger not being able to read this anymore. This is a bug.
In 4.3 there is a completely new debugger anyway which will work a lot better. However, due to time constraints it won't have profiler-functionality like that at the time of release. You could file a ticket for it if you use this a lot.