That helps a little, but fundamentally the runtime of a module is still "billed" to the svchost.exe process as a whole - so if a particular one is at 100% of a cpu, you can't tell which module is causing the problem.