When you run an instrumented program, Purify reports all problems that it detects in the third-party libraries that your program uses. Although you can't edit this code to fix the problems, there are compelling reasons to review the messages that Purify reports about the code.
The reliability and quality of your application depend on the third-party code you include in it. When Purify detects errors or warnings in third-party code, you can develop a workaround or use an alternative product from another vendor. You can also request that your vendor fix the problems (or even Purify its product!), to help ensure that the components you build into your application meet your high standards.
It's possible that your own code is causing error reports to appear in the third-party code. Unless you check the third-party code, you can't uncover the errors in your code. For example, if your code allocates an undersized buffer and then passes the buffer into a third-party routine to receive an argument, the buffer overwrite occurs within the third-party code. Purify detects these errors.