NETWORK SERVICE support

A set of changes to support a major use-case I have of gathering system test coverage data from a constellation of services running as Network Service, and now seeing daily use.

1) Fix service profiling by ACLing the shared objects to the service principal (read/write only is sufficient for the shared memory so far as the service is concerned) as well as the current user
2) For the case when there may be multiple services running under the same principal being started concurrently, allow manual selection of profiler injection to the service environment to be performed for the service name rather than the service principal (to avoid any possible races).
3) Heed the output of VS2013 static analysis and clean out noise.

Probably a more useful change than my previous patch (to partcover at http://sourceforge.net/p/partcover/code/35/)