Remove the comments about iterator validation

As it may be implementation dependent.

src/google/protobuf/map.h

@@ -504,9 +504,7 @@ class MapPair {
 //  assert(m0.begin()->first == m1.begin()->first);  // Bug!
 //
 // Map's interface is similar to std::unordered_map, except that Map is not
-// designed to play well with exceptions.  Mutations to a Map do not invalidate
+// designed to play well with exceptions.
-// a Map's iterators, pointers to elements, or references to elements.  Except
-// for erase(iterator), any non-const method can reorder iterators.
 template <typename Key, typename T>
 class Map {
  public: