Sometimes it would be nice to be able to drill down through all the members and local variables in the reported stack trace. For instance, I received an error from a user that was caused by a member variable that is a class. This variable has other members that I would have liked to inspect. Right now the report shows whether the sub-member is null, or what type it is, but no other details (except for arrays).
I realize there may be tradeoffs between complexity, speed, and size of the error report. Perhaps we could include an attribute on classes or specific members that the report can drill down into?