Broaden README header to cover timestamps, oracles, and counters

The old header only mentioned ETH's 18 decimals. The rewrite grounds
the cost (20k gas per extra slot) and names the full range of on-chain
values that benefit from quantization.

Author: 0xferit

README.md

@@ -3,7 +3,9 @@
 [![Staking Case: Gas Usage Reduction](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/0xferit/uint-quantization-lib/gh-badges/.badges/staking-savings.json)](test/showcase/ShowcaseGas.t.sol)
 [![Extreme Case: Gas Usage Reduction](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/0xferit/uint-quantization-lib/gh-badges/.badges/extreme-savings.json)](test/showcase/ShowcaseGas.t.sol)
 
-Ethereum values use 18 decimals of precision: far more than most contracts need. Trade that excess precision for storage density. Quantize uint256 values into fewer bits than their range requires, packing more data per slot and saving gas.
+Token amounts carry 18 decimals of precision. Timestamps fit in 40 bits but live in `uint64`. Oracle prices, counters, accumulated fees: most on-chain values use far more resolution than the application needs, and every extra storage slot costs 20,000 gas on a cold write.
+
+This library quantizes `uint256` values via right-shift compression, packing more fields per storage slot and cutting gas on every write.
 
 **Quick start:**