reduce verbosity of runtime messages

[kroening]

The time taken for particular steps is statistics, not status.

• Each commit message has a non-empty body, explaining why the change was made.
• n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.35%. Comparing base (ef327f6) to head (4942546).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #8354   +/-   ##
========================================
  Coverage    78.35%   78.35%           
========================================
  Files         1726     1726           
  Lines       188405   188405           
  Branches     18446    18446           
========================================
  Hits        147634   147634           
  Misses       40771    40771           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.