Added possibility to disable constructor mapping for a profile

We are using profiles, and I wanted to be able to disable constructor mapping, but there didn't seem to be any way to configure this in a profile, so I added it.

It would actually been enough for me if I could turn off constructor mapping globally for all profiles in some way, but it doesn't seem like the global configuration is propagated down to the different profiles. I don't know if that is a bug or not, but this small addition to Profile.cs would solve it for us.