DotMemory attach to process Follow

I'm attempting to run DotMemoryUnit with my automation tests to check if the UI is leaking memory anywhere (our most common problem)

General process is outlined in this stack overflow question.

https://stackoverflow.com/questions/51672982/dotmemory-error-comparing-snapshot-to-itself

The issue I'm having is that rather than getting a memory snapshot for my application, it's instead returning a memory snapshot for what I'm assuming is the testrunner.

As such, is there any way to tell DotMemory or DotMemoryApi a process ID that it should be looking at?  Or any other / better way I should be handling this test?