The default StyleCop rules do run counter to VS2015's recommended style guide, and you can point that out if you wish. That said, if OP is using StyleCop, it's part of a requirement (and should be treated as much of a requirement as using a thread to solve Sieve is in a particular question).
I wouldn't say StyleCop is bad - it's great at enforcing consistency - and I don't think StyleCop being good or bad should found the basis of a review, but rather be a single point in that review.
I think it would be worth mentioning to OP that his rules run counter to the .NET guidelines, but if that is what his team is using, then that's what he's going to have to stick with.
Reading your specific answer, I would say that while I agree with you, I'm not sure what you've put there is substantive enough for a review given that OP is using StyleCop. Your answer ultimately comes down to an opinion, though, rather than a review that actually adds value to the OP's code, IMO.
I do think OP should have mentioned he was using StyleCop in his OP.