[FS#1030] Add, use, and test DUNE_ASSERT_BOUNDS

If DUNE_CHECK_BOUNDS is defined, DUNE_ASSERT_BOUNDS checks if a condition holds; otherwise, it does nothing. It is meant to be used for conditions that assure writes and reads do not occur outside of memory limits or pre-defined patterns and related conditions.

Replacement for assert in relevant context; guarded by a single universal define rather than existing class- or module- specific ones.

dune/common/test/CMakeLists.txt

@@ -7,6 +7,16 @@ dune_add_test(SOURCES bigunsignedinttest.cc
 
 dune_add_test(SOURCES bitsetvectortest.cc)
 
+dune_add_test(SOURCES boundscheckingtest.cc
+              COMPILE_DEFINITIONS DUNE_CHECK_BOUNDS=1
+              LINK_LIBRARIES dunecommon)
+dune_add_test(SOURCES boundscheckingmvtest.cc
+              COMPILE_DEFINITIONS DUNE_CHECK_BOUNDS=1
+              LINK_LIBRARIES dunecommon)
+dune_add_test(SOURCES boundscheckingoptest.cc
+              COMPILE_DEFINITIONS DUNE_CHECK_BOUNDS=1
+              LINK_LIBRARIES dunecommon)
+
 dune_add_test(SOURCES calloncetest.cc
               LINK_LIBRARIES dunecommon)