pointer checks are now fatal

[kroening]

The checks for

• pointer dereferences
• pointer relations
• pointer arithmetic

are designed to identify cases of undefined behavior. They must be fatal.

• 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).
• n/a 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.

[tautschnig]

Approving of the overall approach, but more test specs need to be updated (more UNKNOWN properties).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.34%. Comparing base (ed51462) to head (2c19fb9).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #8316      +/-   ##
===========================================
- Coverage    78.34%   78.34%   -0.01%     
===========================================
  Files         1722     1722              
  Lines       188369   188369              
  Branches     18456    18454       -2     
===========================================
- Hits        147572   147569       -3     
- Misses       40797    40800       +3     

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