The debug panel in wicket-devutils uses WicketObjects#sizeOf() to calculate
the size of the page and the session.
The "problem" that I see is that it calculates the size of the non-detached
object. I think what really matters is the size after detaching it, because
this is what is being saved in the http session and the disk, and I guess
this is what the developer needs to know actually.