Namespace collision when running the tool on the standard library

[EarlPitts]

Due to the way the peer nodes have their load paths modified, running the checker on module that has the same name that the peer modules use internally leads to problems.
For example, if we try to run the checker on the re module from the standard library, the peer node itself cannot even start, because starting it requires same functions from re, but because of the modified load path, it would try to find the function in the module to be checked.

One way to resolve this issue would be to modify the load path just before the function that needs to be tested is evaluated, but that could probably lead to other issues, so more investigation is needed.