A couple users have reported issues with using the Custom Path policy with the Code Analysis policy. The Custom Path policy is part of the Team Foundation Power Tools, and can you can get the bits for free from the Microsoft Web site.

The Custom Path policy allows you to scope a check-in policy to specific source control paths and file types. Unfortunately, it appears that the Custom Path policy doesn't play nicely with the Code Analysis policy. I was able to reproduce this by adding a Code Analysis check-in policy, and then creating a Custom Path policy to scope it. The result is that the Code Analysis policy doesn't run at all. For any path, though it works successfully as a standalone policy.

I opened up a bug on the Microsoft Connect portal, so for those that may experience this issue I recommend you go and validate the bug, and provide any additional feedback you may have.