Why does the CLR persistence technique require separate DLLs for 32-bit and 64-bit systems, and how does the POC handle this?

The CLR profiler runs in the same bitness as the .NET process, so a 32-bit DLL is needed for 32-bit processes and a 64-bit DLL for 64-bit processes. The POC registers both under `HKCU\Software\Classes\CLSID\{CLSID}\InProcServer32` (for 64-bit processes) and under the WoW6432Node path (for 32-bit processes), ensuring that both types of .NET programs are hijacked. This redirection issue is common in 64-bit environments.