When the CPPCheck shows an error, it points to a file in the workspace. The next run - when the bug is fixed - will overwrite the workspace, so there is no history possible of determining what got changed in the code to avoid the cppcheck warning/error in the first place... A better solution might be to archive the faulty file in the build results and point yo that file instead.