You will receive a batch of individual C source lines.

Rank the items by how likely the exact line is a useful object-use site for later
use-after-free analysis. This pass identifies possible USE sites only; the
corresponding FREE is not present. Do not try to determine whether a complete
use-after-free exists.

A USE site is executable code that actually relies on an existing object or
subobject remaining valid. It may dereference a pointer, access a field through
a pointer, read or write through an object, pass a pointer-like object to another
function, invoke through a function pointer stored in an object, inspect object
state, index through an object, or otherwise use an object whose lifetime
matters.

Do not require the literal word "use". Project-specific helper calls may be
candidate USE sites when the visible operation and arguments suggest that an
object is being accessed, inspected, modified, passed onward, or otherwise
relied upon while expected to remain valid.

Rank higher executable lines that directly access, inspect, pass, dereference,
index, read from, write through, or invoke through an object. This includes:

- field reads and writes through an object;
- calls that pass pointer-like objects or object-owned subobjects;
- indirect calls through an object's operation table or callback;
- lock and unlock operations on object-owned locks;
- state, flag, length, type, and reference-count checks on objects;
- conditions whose evaluation itself accesses an object or subobject.

A branch is not control-flow-only when evaluating its condition reads,
dereferences, indexes, or otherwise relies on an object. Judge the operation
performed while evaluating the line, not merely the statement keyword such as
`if`, `while`, or `return`.

Do not rank reads below writes merely because reads do not modify state.
Reading, checking, comparing, passing, or invoking through an object can depend
on its validity just as much as writing through it.

Judge only the operation visible in the supplied line. Do not infer an unshown
operation merely from the English meaning of a comment, constant, identifier,
type name, macro name, or nearby code.

Calibration examples for this USE pass:

- `value = node->next;` or `node->next = value;`: score 3.
- `result = device->ops->submit(device, request);`: score 3.
- `if (request->length > limit)`: score 3 because evaluating the condition reads
  a field through an object.
- `helper(context);`: score 1, 2, or 3 depending on how directly the visible
  function and argument establish meaningful object use.
- `spin_lock(&queue->lock);` or `spin_unlock(&queue->lock);`: score 2 or 3.
- `struct record *record;`: score 0.
- A function declaration or definition signature: score 0.
- A comment describing an object access: score 0.
- `if (err)`, `goto out;`, or `return 0;`: score 0 when the exact line exposes no
  meaningful object use.
- Constants, enum entries, labels, directives, and table or operations
  initializer entries: score 0.

The later comparison phase may correct a mistaken preliminary score. Rank by the
original USE-site criterion after considering all candidates, not merely by
sorting the score digits.
