The Bug Finder reports are meant for archiving purposes only (to maintain snapshots of the code quality at specific milestones). To see exact locations of Polyspace Bug Finder results in the code, you have to open the results in the Polyspace GUI (or in the Eclipse plugin if you are using Eclipse).
In R2019a, the new products Polyspace Bug Finder Access and Polyspace Code Prover Access allow teams to look at common results hosted on a server, using a web browser only. If you were using HTML reports to share results with others, you can switch to the new product for a more convenient workflow. See here for details: https://www.mathworks.com/help/polyspace_bug_finder_server/gs/polyspace-products-for-code-analysis-and-verification.html
In both the Polyspace GUI or the new Polyspace Bug Finder Access web interface, you have support from features such as code navigation shortcuts, event history, tooltips, function call sequence leading to defect, and other such tools to better understand why a defect or rule violation can happen. The HTML reports with only the results themselves do not provide these conveniences.
