Perhaps *Matched would be a bit more naming here. I was biased by the existing `MatchableDataTable` which was initially created for different purpose and now I used the same name.

So we have:
1. Pure underlying data (more or less passive; maybe some basic equality comparison; presently there is toStringValue conversion): DataTable, DataRow. 
2. Wrappers around these: for reporting purposes. (Labelling name, value as string).
3. There is some other responsibility to support the *matcher*: like comparing Cell vs Cell; Row vs Row.
  - At some moment I've been thinking to put this into the same wrappers from point 2.
  - But it may make sense to add another class/interface for that.
  - Could be *matcher* itself if it's something which is specific to the comparison algorithm. But that's bloating the Matcher.
  - Some "basic" part like the conversion toStringValue e.g. for DataRow is in (1) at the moment

I'll experiment a bit to see where it goes.