I am reading the following stuff from the research paper at: Restricted Transfer
We define a property that guarantees that ether transfers (via call) cannot be invoked by any user a. Violation of this property can detect Ponzi schemes . Our compliance pattern requires that for all users, invocations of that call instruction do not transfer ether. Our first violation pattern checks if the call instruction transfers non-zero amount of ether and its execution is independent of the sender. For the second violation pattern, the amount of ether transferred depends on the transaction data (and thus can be set to a non-zero value), while the execution is independent of this data (and will thus take place).
It look like that the tool (Securify) eliminates transfers by 'call' by declaring them vulnerable. If this is the case then what are the other ways of transferring Ether at the bytecode level?