PR# 12169 Hit count shown in Breakpoints tool not zeroed when execution ends

The hit count displayed in the Breakpoints tool is not reset to zero
when system execution ends (or perhaps it should be when system execution
starts again) when Force Debugger Mode is enabled.
This results in confusing display, since the hits from
the previous execution of the system are still shown in Breakpoints tool
but the Hit Count menu item from right clicking on that same breakpoint
shows zero.

Compile sample graphical application.
Put breakpoint on {ANY}.default_create.
Click on Show Information About Breakpoints button.
Expand `default_create' in that window to see individual breakpoints.
Click on Force Debugger mode button.
Click on Start.  Breakpoints window shows "enabled (1 hit)".
Click on Continue 3 times.  Application exits.  Breakpoints window
  shows that there are 3 hits for `default_create' even though application
  has exited.  This may be OK so far, since it might be useful to know
  how many times the application stopped at that breakpoint even after
  application exits.  But note that right-clicking on the breakpoint in
  the Feature Relation tool and selecting Hit Count shows 0 hits at this point.
Click on Step into Routine.  Breakpoints window still shows 3 hits
  for `default_create' but should show 0 hits (i.e., the "(3 hits)"
  portion should be cleared).
Click on Continue.  Now Breakpoints window correctly shows "1 hit".

Note that we reset the hit count values when starting a new debugging session.
This way, the user can still consult the hit count value when the application is exited.

Those issues related to Hit count are now fixed by revision rev#68064

A related problem (which might need a separate fix) is that selecting Hit Count
for a breakpoint and then resetting its hit count to zero via the Reset button
does not update the Breakpoints window to show zero hits for that breakpoint.