CBMC 5.72.1 point release for #7401

[TGWDB]

• Each commit message has a non-empty body, explaining why the change was made.
• 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.
• White-space or formatting changes outside the feature-related changed lines are in commits of their own.

[codecov]

Codecov Report

Base: 78.41% // Head: 78.41% // No change to project coverage 👍

Coverage data is based on head (61c0372) compared to base (2653d78).
Patch coverage: 93.02% of modified lines in pull request are covered.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #7422   +/-   ##
========================================
  Coverage    78.41%   78.41%           
========================================
  Files         1655     1655           
  Lines       190264   190264           
========================================
  Hits        149201   149201           
  Misses       41063    41063           

Impacted Files	Coverage Δ
...strument/contracts/dynamic-frames/dfcc_library.cpp	95.54% <ø> (ø)
...cts/dynamic-frames/dfcc_lift_memory_predicates.cpp	89.60% <40.00%> (ø)
src/ansi-c/c_typecheck_expr.cpp	75.68% <100.00%> (ø)
...ument/contracts/dynamic-frames/dfcc_instrument.cpp	81.44% <100.00%> (ø)
...contracts/dynamic-frames/dfcc_pointer_in_range.cpp	100.00% <100.00%> (ø)
...t/contracts/dynamic-frames/dfcc_pointer_in_range.h	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.