A review now mixes allocation choices, benchmark records and lazy sequences. Preserve the requested output while changing storage or work only where the contract calls for it. The fresh examples include empty data, an immediate iterator stop and a measurement with no operations. A capacity reservation must not create extra logical elements, and a tiny retained result must not alias its source when the caller needs independence. The benchmark records are fictional evidence for calculations. They do not establish that one browser run is faster than another. You have already used each needed operation. Explain the ownership rule or measurement denominator before you edit, then check the normal case after fixing the boundary.