Field Base conflict (with BEF Test Content Feature)

Greetings, I understand that I am only supposed to declare a field base once (e.g. the standard "body" field) across various features, and then use instances of that field in the other features. However I have a logistical question:

1. We have a multiple content features that are using the standard "body" field, and we have included it as a base field in only one of those modules.

2. However, the Better Exposed Filters module (which was already installed on the site) is packaged with a Feature called "BEF Test Content" -- this feature also includes the "body" field as a declared Field Base.

3. Therefore, our module is immediately in "conflict" state whenever the Better Exposed Filters exists.

Is there a way to resolve this conflict?

I could remove the "body" field base from all of our features, but then what would happen if we install on a site where BEF Test Content feature does not exist? I certainly don't want to rely on a "test" feature that may or may not exist on a given site.