I recalled some similar complaints earlier on the forum. Check here and here for those exchanges. These tells us nothing about 2.0, but your experience indicates it's still a problem. I haven't experienced this issue, but perhaps I haven't tried to override a default assignment.
We thought we had fixed this. However, there are some conditions where it will still happen. We have now fixed the issue and it will be in our next maintenance release.