<ncoverexplorer> task's <exclusions>: what about <inclusions

<ncoverexplorer> task's <exclusions>: what about <inclusions

Does anyone think it will be beneficial to have an <inclusions> block alongside with the exsiting <exclusions>? I guess it will have to be supported in NCoverExplorer GUI as well.
My point is: sometime the list of exclusions get thicker without any wildcard to help around. In many of these cases <inclusions> of elicited assemblies will be mouch more easier to maintain.
I have this kind of problem with two (dependant) "client" <-> "server" projects.

I'd like to hear what other's people (and of course Kiwidude 's) opinion is.

thanks,
~M

---