The SPON Core/Rangefinder inside ACE is exactly the same as the only released separately, so it can be used in exactly the same way. Thus when you play ACE, there is no difference to having SPON Core and SPON Rangefinder loaded separately.
Your situation depends on what exact combination of addons and mission scripts you have running:
* SPON Core addon or mission script: OK.
* SPON Core addon + any SPON component addons: OK.
* SPON Core mission script + any SPON component mission scripts: OK.
* SPON Core, or any SPON component, running as both addon and mission script at the same time: OK (Addon takes precedence, but will still be configured by the settings meant to affect the mission).
* SPON Core mission script + any SPON component addons: Not OK (SPON component addons always require SPON Core addon).
* SPON Core addon + any SPON non-GUI component mission scripts (does not have a ui directory, such as SPON Scuba or HoloMap): OK
* SPON Core addon + any SPON GUI-based component mission scripts (i.e. has a ui directory, such as SPON Map or Recognise): OK, but needs a workaround.
The workaround is to just to add a small part of Core to your mission (25k, so a lot smaller than whole of SPON Core):
* Place a "Game Logics\SPON\SPON Core: Requre" logic object in the mission editor, to ensure that it can't be played without having the SPON Core addon loaded.
* Include the SPON\Core\ui folder (just hpp files), leaving out all the scripts and other bits of SPON Core.
* At the top of the description.ext:
Remember that you can just leave SPON Core mission scripts in your mission and you have no problems at all (all you are doing is wasting some space). This is the simplest option and does not require that the mission be played with SPON Core addon, so is the one I recommend really.
Sorry that this issue is relatively complicated, but you have to remember that virtually no other ArmA modder releases addons and script versions of the same items, let alone ones that are so cross-compatible and simple to use