Improve code quality by resolving compiler warnings

In 2.0 we have turned on many more compiler warnings. This creates a whole avalance of compiler warnings, which we cannot maintain during the release. Except from some low-hanging fruit that can/need be resolved quickly, we are forced to turn off again some warnings. This however needs to be reverted, and the compiler warnings should be resolved or explained.