The SUR Exporters offers you the possibility to export a SUR file consisting of multiple components. So, having already defined destructible groups for my ship's CMP, I did the same for the SUR, so that the SUR and CMP groups match exactly. This, I think, must be done, otherwise there would still be a collision detection when the according group of your CMP is long gone, i.e. shot or blasted off.
Now the question is: How does Freelancer match the SUR and CMP groups, so that collision detection stops at the component blasted off and not another one. I have though of two possibilites. The first would be that the name has to match the name of the component defined in the CMP. But since the SUR exporter doesn't create those names like the CMP exporter does, I think the second possibilty, namely only the order of the groups is relevant, seems more likely. However, the shield sphere group is being inserted after the first group. If you import existing original SURs with the SUR exporter, you'll get this sphere at second position of the groups, too. Now this group must be ignored by Freelancer when matching the groups with the CMP for the second possibility to work correctly.
Of course it could also be an error of the SUR importer. It has another one as well: It lists all groups of the SUR twice and shows the "copies" at wrong positions, while HardCMP shows the SUR file correctly.
Could one of the makers of the exporter / importer say something about that? Was it overlooked or is this supposed to be like that?
Another question: What does this sphere that is created do? As far as I could see, it has something to do with the shield? What's it all about? I thought the shield shape was created by the CMP.
Oh, and here are a few tips for users of the exporter:
1) Always disable the "DirectX Mesh Reduction" as it will come up with "Weld errors" and screw up the details of your model. At least it did with the one I tested it on.
2) Don't use FLModelTool to scale multiple-component SUR files, as it will screw up the overall positions of the components. Again, this is only what I noticed and does not necessarily have to apply to you as well.