Fix references to container requirements tables.

LWG issue 704 ("MoveAssignable requirement for container value type overly strict") added a reference from [associative.reqmts] to what was at the time table 93 ("Allocator-aware container requirements").

That table is now table 86, but the cross reference is now (incorrectly) to table 83 ("Container requirements").  It should still refer to the Allocator-ware container requirements table.  This patch changes it to do so, matching what the committee voted in (many years ago).

Author: jdennett

source/containers.tex

@@ -1559,7 +1559,7 @@
 The associative containers meet all the requirements of Allocator-aware
 containers\iref{container.requirements.general}, except that for
 \tcode{map} and \tcode{multimap}, the requirements placed on \tcode{value_type}
-in Table~\ref{tab:containers.container.requirements} apply instead to \tcode{key_type}
+in Table~\ref{tab:containers.allocatoraware} apply instead to \tcode{key_type}
 and \tcode{mapped_type}. \begin{note} For example, in some cases \tcode{key_type} and \tcode{mapped_type}
 are required to be \tcode{CopyAssignable} even though the associated
 \tcode{value_type}, \tcode{pair<const key_type, mapped_type>}, is not
@@ -2176,7 +2176,7 @@
 The unordered associative containers meet all the requirements of Allocator-aware
 containers\iref{container.requirements.general}, except that for
 \tcode{unordered_map} and \tcode{unordered_multimap}, the requirements placed on \tcode{value_type}
-in Table~\ref{tab:containers.container.requirements} apply instead to \tcode{key_type}
+in Table~\ref{tab:containers.allocatoraware} apply instead to \tcode{key_type}
 and \tcode{mapped_type}. \begin{note} For example, \tcode{key_type} and \tcode{mapped_type}
 are sometimes required to be \tcode{CopyAssignable} even though the associated
 \tcode{value_type}, \tcode{pair<const key_type, mapped_type>}, is not