mesh.order() call breaks mesh.domains()

[Jan Blechta]

For unordered mesh containing facet markers like

<?xml version="1.0" encoding="UTF-8"?>
<dolfin xmlns:dolfin="http://www.fenicsproject.org">
  <mesh celltype="triangle" dim="2">
    <vertices size="4">
      <vertex index="0" x="0" y="0" />
      <vertex index="1" x="1" y="0" />
      <vertex index="2" x="1" y="1" />
      <vertex index="3" x="0" y="1" />
    </vertices>
    <cells size="2">
      <triangle index="0" v0="3" v1="0" v2="1"/>
      <triangle index="1" v0="1" v1="2" v2="3"/>
    </cells>
    <domains>
    <mesh_value_collection name="boundary markers of edges" type="uint" dim="1" size="6">
      <value cell_index="0" local_entity="2" value="1"/>
      <value cell_index="0" local_entity="0" value="1"/>
      <value cell_index="0" local_entity="1" value="0"/>
      <value cell_index="1" local_entity="1" value="0"/>
      <value cell_index="1" local_entity="2" value="1"/>
      <value cell_index="1" local_entity="0" value="1"/>
    </mesh_value_collection>
    </domains>
  </mesh>
</dolfin>

loading mesh and writing back to file
    mesh = Mesh()
    mesh << File('mesh.xml')
    mesh >> FIle('mesh_broken.xml')
breaks mesh_value_collection, because mesh.order() call does not correct data in mesh.domains() while renumbering local indeces of vertices in each cell.