Why aren't hidden assembly analyzed?

Some assemblies included in the project are not modified and their analysis makes no sense because there is a 100% guarantee that they have not been modified. For example, it is completely true for the system assemblies of the .NET Framework library.

Why is it necessary to load into the project hidden assemblies if they do not take part in the analysis process?

It is necessary for the built-in disassembler to run correctly. Since the names of types, methods and their parameters are stored inside an assembly they are defined in, it is necessary for the assembly with their definitions to be loaded into the project in order to form the names of these types, methods and parameters.

Can Testing Relief analyze itself?

Yes, it can. Stating from a certain stage of its development, Testing Relief has been used to detect changes in itself. Testing Relief is designed so that project assemblies are loaded into different domains and do not influence each other.

What mechanism does Testing Relief use to analyze code?

To analyze code, Testing Relief uses the Reflection feature from Microsoft .NET Framework 2.0