Trying to debug hacks on objects may be easier with an
object level debugger, especially when the hacked
object is used in conjunction with other non-hacked
objects.
It seems really black box right now trying to track
what is going where when important object methods are
returning absolutely nothing.
The idea is to eliminate adding var_dump() or print()
all over a core file when an object debugger class
could encapsulate all of that