I'll take an orthogonal tack to answering this question from what Peter K has (validly) already proposed. I assert that the 8-significant-figure claim is little more than marketing-speak; while the software may be able to provide you an estimate with that many digits on it, that doesn't mean that they carry any real information!
It appears that the software in question is intended for use with input signals taken from a sound card. Since any frequency measurements that are taken in the digital domain are relative to the sample rate of the input, the rate at which samples are taken is critical if accurate digital frequency measurements are required. The sample rate of the card is going to be driven by a reference oscillator of some kind.
A typical sound card is likely to have a crystal-controlled oscillator that controls its sample frequency. Crystals are very short-term stable, but over the long term (months and years), aging causes their frequency to drift. Further, they can be relatively sensitive to temperature variations, with small amounts of frequency deviation as you sweep the temperature across its specified operating range (which often is something like -10 to +30 degrees Celsius or so). The temperature problem can be addressed using a temperature-controlled crystal oscillator (TCXO, cheap and small) or oven-controlled crystal oscillator (OCXO, expensive, power-hungry and large).
A quality sound card might have a TCXO to provide maximum initial accuracy from the factory at a specified operating temperature. However, typical values for a highly precise crystal cut from the factory are in the 0.1-0.2 parts per million (ppm) range. Therefore, if the intended crystal frequency is 1 MHz, then the crystal's true oscillating frequency can vary by ~0.2 Hz or so. For most purposes, this is actually quite sufficient. However, if one wants to measure a particular frequency with 8 significant figures, this falls short: the reference oscillator used by your sampler has much more error than the software purports to provide, an example of false precision.
If you truly wanted to build a system that was capable of measuring frequency that accurately, you would need a very accurate frequency reference to compare it against. A couple ways you could do that would be:
Use more expensive hardware. Rubidium frequency standards could be used for this sort of application. They typically provide frequency accuracies in the $10^{-4}$-ppm range or so over long periods of time, so a Rubidium standard could be used as the reference oscillator for a sampler.
Borrow expensive hardware to calibrate your cheap hardware. The frequency error in your sound card is likely to be pretty stable for a short period of time, so you could use a calibration procedure to estimate what the sample rate error in your card is. However, there's no free lunch: you need to get a very accurate signal source to perform the calibration, which could be just as difficult as the first option. Also, the calibration would only be valid in similar environmental conditions for a limited period of time.
While I've provided a simplified treatment of the problem above, the analysis of oscillator accuracy is actually pretty complicated. There are more complicated metrics that are used to characterize oscillator performance in various contexts that might be more appropriate.