Deprecate header and macro dune_static_assert.
Use static_assert instead.

They cased compiler warnings.

DUNE_FINAL is a helper macro for C++11 and should be placed in
std, where now all compatibility has to be placed.
Beautify Doxygen documentation.

sadly the touchpad added some arbitrary "pwd; ", which slipped my
test, as I don't use cmake. Thanks to Andi Buhr for pointing this out.

up to now you could specify a BUILDDIR variable, which implied that modules were built in
$srdir/$BUILDDIR.
Imagine you have your dune modules in $HOME/Src. When you set BUILDDIR=build.g++
your dune-common module is built in $HOME/Src/dune-common/build.g++
Now you change BUILDDIR to an absolute path, e.g. BUILDDIR=$HOME/Build.g++
With the latest change dunecontrol will now build dune-common in
$HOME/Build.g++/dune-common/

Thanks to Angar for bugging me :-)

This patch adds an AutoTools test that tests whether the compiler
supports the 'final' keyword.  It defines the DUNE_FINAL preprocessor
macro, which expands to 'final' if the keyword is supported, and
is empty otherwise.

kudos to Elias Pipping, for details see (FS #1166)
as the new Dune requirements are >= g++ 4.4 we are sure that initializer_list is available.

we install dune.complete into $PREFIX/share/bash-complete/
upto now you have to source the file by hand.

Module names with hyphens are no longer changed to
underscores.
This fixes FS#1432.

Previously running the installed mpi-config failed as mpi-config.m4
was not found. This patch corrects the path to it in the script and
fixes the problem.

remove output and replace it with assertions.

Note remove_reference is necessary, because you cannot extract the iterator type from
row_reference directly in case: row_reference == row_type&