Install the profiler, run it, and then have your developers start running Visual Studio as they normally would, probably for 5-10 minutes. Then stop the profiler. It will give you a report showing you which source processes are causing the most On-Access Scan activity and which files/directories are being scanned.
Awesome, thank you!!