compute_weighted now evaluates only its weighted result instead of building and discarding the distinct-address result, so the zero-weight fallback in the pipeline computes the unweighted measure once. Entries sort stably by address only, so repeated addresses sum their weights in input order for every column and compute_measures matches compute_weighted exactly. A weighted ordered-map reference, shared with the unweighted one, checks IPv4 with duplicates and IPv6.