Proper handling of TESTCODE conditional in Projection class
Fix memory leak in Hitpattern::ScanHits (delete retval of MakeIterator)
Add reconstruction failure reason codes "trkstat"

This variable is available in Tracker, Projection, and Road.
If trkstat == 0, at least one track was successfully reconstructed
in the respective stage. For trkstat > 0, see the header files
for enum ETrackingStatus. These variables assist with investigating
tracking efficiency problems.

In Tracker, "trkstat" replaces the "fail.nhits" and "fail.npat"
status variables.

Also, each Road now reports the 2D fit results even for "failed" fits
(bad chi2). As before, for failed fits, Road::IsGood() is false.
This allows inspection of the entire chi2 distrubution, for example.
Also, clean up the meaning of Road::fGood. It indicates fit success/
failure only, not a build failure (bulding can never fail anyway).
Export plane pattern of best Road fit (good or bad) as "pat"
Minor cleanup in Tracker
Let Tracker print values of flags read from the database during Init
Minor clarifications in SolSpec
Convert the MC hit classes to the new Podd simulation data interface

Also, if requesting MC data decoding, verify that the decoder really
is a simulation decoder. If not, throw Tracker::bad_config.
Make Projection::bad_angle an invalid_argument exception, not range_error
Implement analysis of MC truth information in GEMPlane::Decode
Move definition of Node_t to Hit.h (since it needs HitSet)
Remove leftover old definition of GetTrackerSafe in Plane.h
Let Tracker::ReadDatabase catch all exceptions from MakePlane
Clarify comments in GEMPlane::ChargeDep
For MCdata, update hit info in MCTrackPoints supplied by the SimDecoder

Still to do:
- Update with info from both nearest hit found and actual MC-matching hit.
  If nearest hit != MC-matching hit, indicate this in the status (~soft fail)
- Update track info (reconstructed vs. true track points).
  Much harder because there can be multiple reconstructed tracks.
Fix BAD bug in GEMPlane::ChargeDep

No idea why amp[0] == 0 or amp[1] == 0 should cause failure. This
sneaked into the SBS version on Mar 29, 2011.