Keep Running feature change in behavior

During testing I've noticed some undesirable behavior of the Keep Running feature under certain scenarios. Under one scenario, it kept launching the process over and over due to a misconfiguration caused by the new beta automated updater.

One, in the next beta build process instances will be counted by base names. The path names don't have to match up, as they previously did. I can provide an option if anyone needs the old behavior. That means if you want to keep c:\windows\system32\notepad.exe running, a copy running in c:\test\notepad.exe will already count. This was not true before, and the desired behavior is debatable.

I also tweaked the delay after startup at which it begins even caring about these keep running processes. It is based on your hardware, but there is a delay of at least X iterations before any keep running process is applied. This was true of previous versions too, it has simply been changed.

Additionally, I added a last minute verification that the process didn't suddenly get launched right before us with a new check of the NT processes and threads array.

Lastly, the child process has different flags associated with it, as I noticed applications launched by the governor were sometimes getting Process Lasso's shell icon in the taskbar. This should alleviate that problem, and potentially other problems, as the process is now less a child of the governor. Strangely, there seemed to be no rhyme or reason to whether Windows shell opted to use this icon or not. I do not know if it is an issue with the infamous shell icon cache or not, but I seem to have fixed it where it did appear (it didn't appear on a VM with the same config, so go figure).